Taxonomy driven site navigation

ABSTRACT

Embodiments of the present disclosure provide a method and system for generating a uniform resource locator using one or more terms in a hierarchical taxonomy. Specifically, embodiments disclosed herein provide receiving a plurality of terms for a term set and generating a hierarchical taxonomy for the term set using the plurality of terms. Once the hierarchical taxonomy has been generated, a navigation property may be assigned to at least one term in the plurality of terms. A navigation term set that mirrors the properties of the hierarchical taxonomy is then created using the at least one term.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 13/730,577 (now U.S. Pat. No. 9,311,373) filed onDec. 28, 2012, entitled “Taxonomy Driven Site Navigation” whichapplication claims priority to U.S. Provisional Application Ser. No.61/724,828 filed on Nov. 9, 2012, entitled “Taxonomy Driven SiteNavigation, Page Model and Commerce Site” which are incorporated byreference herein in their entirety.

BACKGROUND

Modern content management systems rely heavily on hierarchies fororganizing data. Such content management systems can be found inelectronic commerce web sites, news publishing portals, knowledge bases,and intranet collaboration sites. Traditionally, each component of acontent management system may need to be manually updated when one nodein the hierarchy is updated or changed. Such changes may be demanding ontime, cost and energy and may be subject to human error.

It is with respect to these and other general considerations thatembodiments have been made. Also, although relatively specific problemshave been discussed, it should be understood that the embodiments shouldnot be limited to solving the specific problems identified in thebackground.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailDescription section. This summary is not intended to identify keyfeatures or essential features of the claimed subject matter, nor is itintended to be used as an aid in determining the scope of the claimedsubject matter.

Embodiments of the present disclosure provide a method and system forgenerating a uniform resource locator using one or more terms in ahierarchical taxonomy. Specifically, embodiments disclosed hereinprovide receiving a plurality of terms for a term set and generating ahierarchical taxonomy for the term set using the plurality of terms.Once the hierarchical taxonomy has been generated, a navigation propertymay be assigned to at least one term in the plurality of terms. Incertain embodiments, a navigation term set that mirrors the propertiesof the hierarchical taxonomy is then created using the at least oneterm.

Embodiments may be implemented as a computer process, a computing systemor as an article of manufacture such as a computer program product orcomputer readable media. The computer program product may be computerstorage media readable by a computer system and encoding a computerprogram of instructions for executing a computer process. The computerprogram product may also be a propagated signal on a carrier readable bya computing system and encoding a computer program of instructions forexecuting a computer process.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments are described with referenceto the following Figures in which:

FIG. 1 illustrates a system for accessing, generating, and editing termsin a term store of a hierarchical taxonomy according to one or moreembodiments;

FIG. 2 illustrates a method for creating a navigation term set using ahierarchical taxonomy according to one or more embodiments;

FIG. 3 illustrates an exemplary user interface for displaying andediting the properties of a taxonomy term according to one or moreembodiments;

FIG. 4 illustrates an exemplary template page according to one or moreembodiments;

FIGS. 5A and 5B illustrate exemplary user interfaces for displaying andediting the properties of a taxonomy term according to one or moreembodiments;

FIG. 6 illustrates an exemplary web page for a given item in a productcatalog according to one or more embodiments;

FIG. 7A illustrates an exemplary user interface for displaying andediting the properties of a taxonomy term including catalog URLsaccording to one or more embodiments;

FIG. 7B illustrates an exemplary user interface for editing catalog itemproperties in a product database according to one or more embodiments;

FIG. 8 illustrates a tablet computing device for executing one or moreembodiments of the present disclosure;

FIG. 9 illustrates a block diagram of a computing environment suitablefor implementing one or more embodiments disclosed herein;

FIG. 10A illustrates one embodiment of a mobile computing deviceexecuting one or more embodiments disclosed herein;

FIG. 10B is a simplified block diagram of an exemplary mobile computingdevice suitable for practicing one or more embodiments disclosed herein;and

FIG. 11 is a simplified block diagram of an exemplary distributedcomputing system suitable for practicing one or more embodimentsdisclosed herein.

DETAILED DESCRIPTION

Various embodiments are described more fully below with reference to theaccompanying drawings, which form a part hereof, and which show specificexemplary embodiments. However, embodiments may be implemented in manydifferent forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the embodiments to those skilled in the art.Embodiments may be practiced as methods, systems or devices.Accordingly, embodiments may take the form of a hardware implementation,an entirely software implementation or an implementation combiningsoftware and hardware aspects. The following detailed description is,therefore, not to be taken in a limiting sense.

Traditionally, there are three distinct components in typical contentmanagement systems. These components are: (i) the taxonomy/taggingportion, (ii) the Uniform Resource Locator (URL) namespace, and (iii)the navigation menu tree. Typically, each component has its ownadministrative user interface and data storage. Thus, when one item forone of the components is updated or changed, corresponding data items ineach of the other components may also need to be manually updated. Forexample, when the phrase “used cars” is replaced with the term“pre-owned vehicles” in a given URL of the Uniform Resource Locatornamespace, similar changes may need to be made to the taxonomy/taggingportion and the navigation menu tree. Continuing with the example, theupdates may include: (i) updating a taxonomy term of “Used Cars” to“Pre-owned Vehicles”, (ii) updating the web page URLs from, for example,“http://example.com/used-cars/2008-camry” to a pattern such as“http://example.com/pre-owned/2008-camry”, and (iii) updating anavigation menu tree. As used herein, a navigation menu tree is ahierarchy of page titles with hyperlinks that is used to drive thewebsite menus, the breadcrumbs (e.g. “Vehicles>Pre-ownedVehicles>Camry”), the site map page (i.e., a summary page that shows theentire menu hierarchy in a flat list), and other navigation controls.

Based on the above, embodiments described herein describe ataxonomy/tagging system that is used to represent data for allcomponents in a content management system. That is, data in thetaxonomy/tagging system is used to represent and build the navigationmenu tree and a URL of a given site. Accordingly, when data in thecontent management system is updated or changed, the need for manuallyupdating each component in the content management system may beeliminated as the updates are automatically performed. For example, whena taxonomy term is renamed, the corresponding URL and an associated nodein navigation menu tree are automatically updated.

FIG. 1 illustrates a system 100 for accessing, generating, and editing aterm store arranged in a hierarchical taxonomy according to one or moreembodiments. In certain embodiments, a term store contains multiplesecurity groups. Each security group contains multiple term sets, andeach term set contains a hierarchy of terms.

In embodiments described herein, a term acts as a classification tagthat can be applied to documents, photos, or other content objects. Forexample, a news article about the Seattle Mariners might be tagged withthe terms “Baseball” and “Washington.” Such tagging associates thearticle with those keywords in the context of a search box or othertaxonomy-enabled control.

Terms in a term set are organized in a hierarchy. For example, the term“Baseball” could be a child of the term “Sports,” and the term“Washington” could be a child of the term “United States”, which is achild of the term “North America.” Within a term set, this hierarchy ofterms can be arbitrarily deep. However, a term is more than just a name.A term is a rich object that can store alternative text labels, such as,for example, synonyms or international language translations, aninformative description, ownership/permission information, and evenuser-defined freeform key/value data.

Referring back to FIG. 1, the system 100 includes a first client 110 anda second client 120. In certain embodiments, the first client 110 andthe second client 120 may access a server 140 over a network connection130. Although two clients are shown, it is contemplated that fewer oradditional clients may access the server 140 through the networkconnection 130. The server 140 maintains a term store 150 in whichmanaged metadata is stored in the form of term sets and terms. Each termmay include one or more properties with each property having anassociated value. In certain embodiments, a particular term may bereused in various term sets. A term is reused when the term, or aproperty of that term, is associated with or has a membership inmultiple locations or term sets.

Embodiments described herein also use terms as a representation ofnavigation menu tree nodes and as a way to assign URLs for content items(e.g. web pages). Terms used as representations of navigation menu treenodes are called navigation terms and belong to a navigation term set.In embodiments, a structure or hierarchy of one navigation term set maybe pinned to (i.e., mirror) a structure or hierarchy of the terms setfrom which the navigation term set is derived. Additionally, propertiesof the terms in the navigation term set may mirror, at least some, ifnot all, of the property of the terms in the original term set. That is,each of the terms, as well as the properties of those terms, in thenavigation term set are similar to those terms in the original term set.However, it is contemplated that other embodiments provide thearrangement of the terms in the hierarchy may be different in thenavigation term when compared against the structure and arrangement ofthe terms in the original term set. In yet other embodiments, thenavigation term set may simply be the term set in the term store butidentified as both a navigation term set and a “regular” term set (i.e.,a term set that is not a navigation term set).

The following table, Table 1, illustrates a sample term store(Example.com Store) containing an exemplary navigation term set called“Example.com Hierarchy.” The “Example.com Hierarchy” represents anavigation menu and the URLs for an example.com web site.

TABLE 1 Term Store Term set Term Term Example.com Store Example comHierarchy About Us Products Electronics Furniture Outdoors Contact

As shown in Table 1, the name of the term set is “Example.comHierarchy.” The term set includes six terms: “About Us,” “Products,”“Electronics,” “Furniture,” “Outdoors,” and “Contact.” The terms in theterm set are arranged in a hierarchical manner. Accordingly, a firstterm of the term set may be a parent or child of another term in theterm set. Additionally, each child term in the term set may inherit oneor more properties from the parent term in the term set. In embodiments,where a term in a term set is a global term, that term may inherit oneor more properties that are available globally. As each of the terms areorganized into a hierarchical structure, changes to various propertiesof one term may be sent through to all terms. Additionally, changes tovarious parent-child relationships may also be propagated throughout theentire structure.

For example, in Table 1 above, the terms “Electronics,” “Furniture,” and“Outdoors” are child terms of the term “Products.” Thus, if one or moreproperties of the term “Products” is changed, those changes would bepropagated to the terms “Electronics,” “Furniture,” and “Outdoors” aseach of those terms are children of the term “Products.” In anotherexample, if the term “Electronics” was moved in the hierarchy from beinga direct child of the term “Products” to a new term called “HomeElectronics” the parent/child relationship between “Electronics” and“Products” would automatically be updated. That is, when the term ismoved or renamed, this change is also seen as a change in an associatednavigation menu. For example, this update would include automaticallyupdating the taxonomy but also automatically updating the associated URLand navigation menu item. Similarly, if a new term “Computers” was addedas a child node of “Electronics” similar changes would be automaticallymade to the other components of the taxonomy system as was previouslydiscussed.

Referring again to the terms in the taxonomy, each term may have one ormore properties. Additionally, a term property may be a local termproperty or a global term property. A global term property is a propertythat is associated with every instance of a term, regardless of whichterm set the term is used in or reused in. In contrast, a local termproperty is a property that is associated with a term only in thecontext of the term set in which it was applied to the term.

In certain embodiments, each level in the hierarchical taxonomy may beaccessible by different clients. For example, if the hierarchicaltaxonomy is formatted as a tree structure, with each node in the treerepresenting a term, one client may have access to a first level of thetree, including all sub-nodes associated with the first level of thetree, while a second client may have access to a second level of thetree including all sub-nodes associated with the second level of thetree but not have access to the first level of the tree including thosenodes included on the first level and above.

In embodiments, the various nodes in the structure may be added, deletedor modified. Additionally, security permissions for the contentmanagement system may be implemented. In embodiments, the securitypermissions may be in the form of a standard access control list (ACL)for each document or content item. Thus, for example, there might be apage called “Publishing Contacts” that is only readable by members of asecurity group “Authoring Team.” If a visitor does not belong to the“Authoring Team” security group, a trimming feature of the presentdisclosure may cause the system to present an error message to therestricted visitor such as “access denied” when the visitor attempts toview the restricted page. Accordingly, this trimming featureautomatically hides the navigation menu item (or more generally thenavigation tree node) which also affects the bread crumb and othernavigation controls for an audience or user that does not have requisitepermissions.

In certain embodiments, the term store 150 stores data about eachindividual term set, term, and the properties associated with each term.As discussed above, the properties include whether the term is marked asa navigation term for a navigation term set. Such data may be stored inone or more tables of the term store 150. For example, the term store150 may include a “Term” table that is populated with data about eachterm, such as, for example, an identifier for each term, with each rowin the table representing a single term. The term store 150 may alsoinclude a “Term set” table that includes information about each termset, such as, for example, an identifier associated with each term setas well as a name of each term set. The term store 150 may also includea “Term Property” table that is populated with term properties and termset properties, such as, for example, if the terms in the term set arenavigation terms.

FIG. 2 illustrates a method 200 for creating a navigation term set usinga hierarchical taxonomy according to one or more embodiments. Method 200begins at operation 210 in which a term set is created. Once created,the term set may be stored in a term store. In certain embodiments acreate term set command may be invoked by a client device using, forexample, a term store manager or other term management tool. The termmanagement tool may be provided to a user of the client device to enableviewing and selection of various terms, term sets and the like. Incertain embodiments, the term store manager or term management tool maybe part of the SHAREPOINT platform by MICROSOFT of Redmond, Wash.Additionally, the term management tool may enable a user to searchcustom properties and synchronize custom properties across various localcopies. The term management tool may also enable a client device toprovide information about local and global terms and the propertiesassociated with each local and global term. The term set may representhow a particular entity or business is organized, such as, for example,the way content is tagged. Additionally, the taxonomy may also show aproduct hierarchy as well as representing various nodes in a sitenavigation. For example, as will be described, settings can be appliedto terms in the term set that affect site navigation as well as URLs ofthe site.

Once the create command is invoked, a user may be prompted to define aterm set name and one or more terms of the term set. In the exampleshown in Table 1 above, the term set is “Example.com Hierarchy,” and theterms in the term set include terms of “About Us”, “Products”,“Electronics”, “Furniture”, “Outdoors”, and “Contact”.

Once the term set has been created, flow proceeds to operation 220 inwhich the term set is designated as a navigation term set. In anotherembodiment, terms in an existing term set, or a new term set such as thenewly created term set, may be copied, reused, or pinned into a secondterm set that has been designated as a navigation term set. In certainembodiments, a term set is defined as a navigation term set based oninput received from a user. It is also contemplated that if a term isadded to a navigation term set after the term set has been designated assuch, that term is also automatically identified as a navigation term,or a term having a navigation property.

In certain other embodiments, if one term of a term set is identified asa navigation term, a copy of the term set is created and identified as anavigation term set. Additionally, each term in the newly generatednavigation term set has a corresponding navigation property. Inembodiments, the navigation term set has the same structure,organization and terms as the original term set from which it wascreated. In another embodiment, when a term in a term set is identifiedas a navigation term, the term set itself is identified as a navigationterm set without a copy being created. As with other taxonomyhierarchies, terms in the navigation term set, as well as associatedproperties, may be updated, added, changed, or removed. In certainembodiments, a term store editor may enable a user to view, update, addor remove the various terms and term properties in a given term set.

Once the navigation term set has been generated, flow proceeds tooperation 230 in which specialized properties for the navigation treeand uniform resource locators are assigned. Specifically, one or morefriendly URLs are generated using the navigation term set. In suchembodiments, the taxonomy terms in the hierarchy may be appended to eachother in a hierarchical manner to define a new “friendly” URL that actsas an alias for, or maps to, an original physical URL. The physical URLis created by an authoring team and is consistent with traditional filesystems. However, the friendly URL allows the URL to be presented usinga concise address. Similarly, the physical URL hierarchy might reflectthe authoring workflow or team ownership, whereas the friendly URLhierarchy might reflect the way customers understand a product catalog(i.e., computers are found in an electronics category, therefore,computers is a child of the term electronics). As will be discussedbelow, the friendly URL may be mapped to a physical URL using a taxonomyeditor.

Table 2 illustrates an exemplary navigation menu item of an exemplarywebsite, an associated taxonomy hierarchy as well as the associatedphysical URL. Likewise, Table 3 illustrates friendly URLs of theexemplary website with each URL being associated with a physical URLmapping.

TABLE 2 Menu Item Taxonomy Object “Home” Example.com Hierarchy  “AboutUs”  “About Us”  “Our Products”  “Products”   “Electronics”  “Electronics”   “Furniture”   “Furniture”   “Outdoors”   “Outdoors” “Contact”  “Contact”

TABLE 3 Menu Item Friendly URL Physical URL “Home” http://example.comhttp://example.com/Pages/Default.aspx “About Us”http://example.com/about http://example.com/Pages/Misc/About.aspx “OurProducts” http://example.com/productshttp://example.com/Pages/Products.aspx  “Electronics”http://example.com/products/ http://example.com/Pages/ElectronicsRollup.electronics aspx  “Furniture” http://example.com/products/http://example.com/Pages/FurnitureRollup. furniture aspx  “Outdoors”http://example.com/products/ http://example.com/Pages/OutdoorRollup.outdoors aspx “Contact” (none) http://example.com/Forms/Contact.aspx

As shown Table 2 above, each menu item of a given website is associatedwith a taxonomy term, which in turn, is associated with a physical URL.Likewise, as shown in Table 3, a friendly URL is generated based on agiven term in the hierarchy. As shown in Table 3, a hierarchy of URLs ispresented. For example, the term “Electronics” is a child node of“Products” in the taxonomy hierarchy and therefore, when a friendly URLthat includes the term “Electronics” is generated, navigation down thehierarchy would result in a friendly URL of“http://example.com/products/electronics.” More specifically, the URL of“http://example.com/products/electronics” is a child of“http://example.com/products” because it appends the URL segment“Electronics” as a suffix. In this way, the taxonomy contributes asingle URL segment for the friendly URL for each term in the term set.Thus, the complete friendly URL is assembled from the chain of parentterms (i.e., “Products” and “Electronics”). As each friendly URL ismapped to a corresponding physical URL, if a user clicks on the menuitem “Electronics” in the example.com website, their browser will showthe friendly URL “http://example.com/products/electronics” rather thanthe physical URL ElectronicsRollup.aspx. Note that by contrast, the menuitem “Contact” does not have a friendly URL, because it is a simplelink.

Because the terms in the hierarchy are associated with a friendly URL,any changes made to the terms in the hierarchy are automatically appliedto the corresponding friendly URL. Thus, for example, if the term “HomeElectronics” was added as a child node to the term “Electronics”, afriendly URL would be automatically generated for an associated physicalURL for the newly created “Home Electronics” web page (assuming a “HomeElectronics” page or a template of the page had been created). Likewise,if the term “Electronics” was moved in the hierarchy to be direct childnode of the Example.com website, the new friendly URL associated with“Electronics” would be “http://example.com/electronics” instead of“http://example.com/products/electronics.”

As discussed above, a navigation menu tree is a hierarchy of page titleswith hyperlinks that is used to drive the web site menus, thebreadcrumbs, and the site map page. The navigation breadcrumb shows thecurrent node from the navigation menu tree. Continuing with the exampleabove, when the friendly URL of http://example.com/products/furniture isviewed, the associated breadcrumb would be “example.com>OurProducts>Furniture.” However, when a site has a lot of pages, not everypage needs to appear in the navigation menu or have an associatedfriendly URL. Accordingly, embodiments provide that these pages may beassociated with a folder that contains a collection of physical URLs tobe associated with a navigation term. For example, the folder“http://example.com/Pages/Press/” could be associated with a new term“Press Releases.” This way, when a user views an article inside thatfolder (e.g., http://example.com/Pages/Press/2012-01-26.aspx) thebreadcrumb would show “example.com>Press Releases” even though there isnot a specific menu item for the document 2012-01-26.aspx.

One or more embodiments also provide a performance optimization thatconsists of a navigation cache that stores a copy of the menu items andassociated URLs in a working memory of a server. Such a configurationallows the server to avoid having to repeatedly retrieve thisinformation from the taxonomy terms.

Additional embodiments provide a link fix-up system that automaticallycorrects links in hypertext. For example, if a user edits the friendlyURL of “http://example.com/used-cars/2008-camry” to“http://example.com/pre-owned/2008-camry,” any HTML content that isreferenced by the old URL will now contain broken hyperlink.Accordingly, for HTML content hosted internally by the contentmanagement system, all pages that link to the page that was updated arealso automatically updated to reflect the change. Similarly, when thephysical URL is changed, such as, for example, because the underlyingcontent object was renamed, the associated taxonomy term isautomatically updated with the new target URL.

One or more embodiments also provide for URL rewriting. In thisapproach, the web server software performs a preprocessing step at thebeginning of the HTTP request, wherein the incoming friendly URL isrewritten (i.e. replaced by) the corresponding physical URL, andsubsequent processing occurs as if the physical URL had been requestedfrom the server.

FIG. 3 illustrates an exemplary user interface 300 for displaying andediting the properties of a taxonomy term. As shown in FIG. 3, the userinterface 300 gives a user the opportunity to: (i) name a term in thetaxonomy, (ii) give a description of the taxonomy term, (iii) name anavigation menu item for the term, (iv) create hover text for thenavigation menu item, (v) input a physical URL, (vi) identify a nodetype, and (vii) describe the friendly URL segment that will be used togenerate the friendly URL. In the exemplary user interface 300, the“Customize” box 305 is checked next to “Navigation Menu Item Title”which indicates that the phrase “Our Products” was input manually,rather than equating the “Navigation Menu Item Title” to the taxonomyterm name (i.e., “Products”). By contrast, the “Customize” box 310 isunchecked for the “Friendly URL Segment” indicating that “products” isgenerated from the term name. In certain embodiments, the friendly URLsegment is generated using a computerized formula which converts lettersto lower case and removes punctuation or spacing characters. In certainembodiments, this may be required as the term name may allow charactersthat are illegal in URLs. Thus, such characters need to be removed orsomehow encoded.

In another embodiment, a content management system may include a“roll-up” page that displays a listing of documents, photos, or othercontent items. These content items may be related to a specific categoryor topic. For example, a news web site might include a menu item“Baseball” which takes the viewer to a page that shows the top 10 mostrecent news stories involving baseball, and also the top 10 most popularstories involving baseball. Similarly, an e-commerce site might have amenu item “Televisions” that shows a filtering control with searchresults for televisions. In such cases, the navigation term set may befurther configured to render pages with such content.

With reference to FIG. 4, the example.com website may have three roll-uppages—one for each of “Electronics,” “Furniture,” and “Outdoors.” Thecontent on these pages is primarily constructed from search results forthe particular category, such as, for example, “10 most popular itemstagged as Electronics” or “10 most popular items tagged as Furniture.”However, rather than creating and maintaining a separate page for eachcategory, it is more efficient to create a single template page which isparameterized by the specific category keyword.

For example, instead of the physical URLs of“http://example.com/Pages/ElectronicsRollup.aspx,”“http://example.com/Pages/FurnitureRollup.aspx,” and“http://example.com/Pages/OutdoorRollup.aspx,” a template page for eachcategory might be structured as:“http://example.com/Pages/ProductsTemplate.aspx?Keyword=Electronics,”“http://example.com/Pages/ProductsTemplate.aspx?Keyword=Furniture,” and“http://example.com/Pages/ProductsTemplate.aspx?Keyword=Outdoors.”

The web parts on the page (e.g. “10 most popular items tagged as X”)will then by driven by a Keyword parameter. Additionally, the navigationterm set allows multiple friendly URLs to be mapped to the same physicalURL (i.e., a template page described above) while keeping the samefriendly URLs of “http://example.com/products/electronics,”“http://example.com/products/furniture,” and“http://example.com/products/outdoors.”

Such a configuration also minimizes management overhead. For example, ifa new term “TVs” is added to the term set (i.e., as a child of“Electronics”), then an associated roll-up page is created automaticallywithout requiring any special configuration effort from the user.Lastly, in contrast to a simple URL parameter such as“Keyword=Electronics”, the Taxonomy system provides a natural storemechanism for additional template parameters such as a category image, acategory description, etc.

Table 4 below illustrates a template where several different friendlyURLs are mapped to or resolve to the same physical URL. In order todistinguish the URLs, a navigation term identifier may be appended tothe Physical URL as part of the URL rewriting operation implemented by aweb server. For example, a physical URL with term context parameters forthe friendly URL “/products/furniture” could be“http://example.com/Pages/ProductsTemplate.aspx?TermStoreId=1001&TermSetId=3013&TermId=4017.”Likewise, the physical URL with term context parameters for a friendlyURL of “/products/outdoors” could be“http://example.com/Pages/ProductsTemplate.aspx?TermStoreId=1001&TermSetId=3013&TermId=4018”(where the terms in the term store of Table 1 above have been assignedterm identifiers added in parenthesis as shown in Table 5 below).

Although URL rewriting is specifically mentioned, it is contemplatedthat the term identifier could be stored in a program variable that isreadable by the controls on the web page. Regardless, the friendly URLmaps to a taxonomy term, which is the input for various controls thatdisplay term-driven content on the page.

TABLE 4 Menu Item Friendly URL Physical URL “Home” http://example.comhttp://example.com/Pages/Default.aspx  “About Us”http://example.com/about http://example.com/Pages/Misc/About.aspx  “OurProducts” http://example.com/productshttp://example.com/Pages/Products.aspx   “Electronics”http://example.com/products/http://example.com/Pages/ProductsTemplate.aspx electronics    “TVs”http://example.com/products/http://example.com/Pages/ElectronicsTemplate. electronics/tvs aspx   “Phones” http://example.com/products/http://example.com/Pages/ElectronicsTemplate. electronics/phones aspx  “Furniture” http://example.com/products/http://example.com/Pages/ProductsTemplate.aspx furniture   “Outdoors”http://example.com/products/http://example.com/Pages/ProductsTemplate.aspx outdoors  “Contact”(none) http://example.com/Forms/Contact.aspx

TABLE 5 Term Store Term set Term Term Example.com Store (Term Store ID =1001) Example.com Hierarchy (Term Set ID = 3013) About Us (Term ID =4014) Products (Term ID = 4015) Electronics (Term ID = 4016) Furniture(Term ID = 4017) Outdoors (Term ID = 4018) Contact (Term ID = 4019)

Referring again to FIG. 4, FIG. 4 illustrates an exemplary template page400. Specifically, FIG. 4 illustrates an exemplary template paged called“ProductsTemplate.aspx” when the template page is driven by the“Furniture” term (having a term ID of 4017 as shown above in Table 5).The exemplary page acts as a template because the content of certainfields in the page changes according to a friendly URL associated withthe template page. As shown in FIG. 4, the template page 400 includes:(i) a title field 410 that reads the navigation text from the term; (ii)a description field 420 that reads the hover text from the term and(iii) web parts 430 that perform searches to display the “10 newest” and“10 most popular” products associated with the term. Although specificfields are mentioned, it is contemplated that additional filed and/orarbitrary key/value data pairs can be stored with a taxonomy term. Suchdata enables users to assign their own application-specific data thatcan also be used to control the template page.

In addition to the above, embodiments provide a setting that enableschild terms in the taxonomy to inherit a default physical URL from aparent term. For example, for a large catalog with hundreds ofcategories, it would be cumbersome to assign the same physical URL toeach navigation term. Thus, in certain embodiments, a setting may beselected whereby a user may select a single physical URL for an entiresub-tree of child terms. In embodiments, this setting may be inheritedby child terms created later.

This setting acts a default value that only applies if there is noexplicit setting. For example, the e-commerce web site might use thesame physical URL for all 100 product categories, except for twospecific categories that have customized pages—embodiments disclosedherein allows this to be achieved by assigning values for only 3 terms,rather than having to assign values to all 100 terms.

To help manage these URLs, when editing a physical page, an editorprovides an option whereby a user may view the various page URLs.Accordingly, the option displays to a user a diagnostic screen thatdisplays the physical URL for the page alongside all of the associatedfriendly URLs.

When an author is viewing a friendly URL and enters a page editing mode,the user may be presented a prompt that asks: “You are about to edit apage that acts as a template for multiple Friendly URLs. Do you wantyour change to affect all friendly URLs, or do you want to edit a copyof the page for a single friendly URL?” The latter option creates a copyof the page template, and then binds the friendly URL to that page whileall of the other friendly URLs remain bound to the original page. Thisprovides a convenient way for the author to create custom content for aparticular category, (e.g. for a seasonal promotion).

In a similar manner, when an author deletes a page with multiplefriendly URLs, the author may be asked whether they want to delete thepage template which will affect all associated friendly URLs or merelyto delete the navigation term thereby affecting only a single friendlyURL.

For simplicity, the examples presented herein involve a singlenavigation term set. However, embodiments provide for multiplenavigation term sets to be active simultaneously. For example, thenavigation menu at the top of the page might provide an overallhierarchy for the entire web site, whereas the left menu might provide aspecialized hierarchy for a particular section. Accordingly, friendlyURLs from two different term sets may be bound to the same target page(i.e. the same physical URL). This is supported by using a compound keyconsisting of the TermStoreId, TermSetId, and TermId, rather thanspecifying only the TermId.

FIGS. 5A and 5B illustrate exemplary user interfaces 500A and 500B fordisplaying and editing the properties of a taxonomy term includingphysical URLs and Default Physical URLs for a given page. Specifically,FIGS. 5A and 5B show an exemplary user interface that displaysproperties of two different friendly URL terms for editing (i.e., FIGS.5A and 5B show the same interface but with two different terms loadedinto the interface for editing). As shown in each figure, each termcontributes only a single segment of the URL, and the full friendly URLis built up by prepending the segments from the chain of parent terms.Additionally, the user does not need to assign the “Physical URL forThis Term” setting for every single term. By assigning the “DefaultPhysical URL for Child Terms” a user can specify a single URL thataffects an entire sub-tree. For example, because the term “Electronics”is a child of the term “Products”, each term may have the same singleURL (e.g., “http://example.com/Pages/ProductsTemplate.aspx”). However,certain embodiments provide that this feature can be overridden. In suchcases, such as shown in the example in FIG. 5B, the physical URL for the“Electronics” term is “http://example.com/Pages/ProductsTemplate.aspx”while the default physical URL for child terms (i.e., TVs, Phones, etc.)is “http://example.com/Pages/ElectronicsTemplate.aspx.”

Embodiments also disclose commerce web sites which are modeled using thetaxonomy features described herein. Specifically, embodiments disclosedherein allow online vendors to construct a new model that allows productdescriptions to exist in a product catalog, or list, while the sitehierarchy and URL structure are managed and modeled in a taxonomysystem. Thus, rather than displaying an existing HTML page for a givenproduct, a query using the current taxonomy term navigation context isexecuted. The query can be modified in real time by the use of queryrules and properties associated to the terms in the taxonomy system.

Embodiments herein provide for catalog URLs that are based on friendlyURLs. In embodiments, the catalog URS are based on a specific item, suchas, for example an SKU number of a particular product, a description ofthe product and the like. Continuing the example above, a friendly URLfor the example.com furniture site may be“http://example.com/products/furniture” while a catalog URL for aspecific item, such as, for example a red sofa, may be“http://example.com/products/furniture/sku01096/red-sofa.”

As discussed above, catalog URL (e.g. “/Pages/ItemTemplate.aspx”, asshown in FIG. 6) is based on a friendly URL (e.g.“/Pages/ProductsTemplate.aspx”, as shown in FIG. 4), but with anadditional suffix (“sku01096/red-sofa”) that does not correspond toterms in the hierarchy. For example, there is not a taxonomy term“red-sofa” nor a term “sku1096,” but rather these segments of the URLare constructed from the Title field (“Red Sofa”) and Item Number field(“SKU1096”) for the catalog item. The catalog item is tagged with the“Furniture” term by assigning the Item Category taxonomy field.Accordingly, embodiments herein provide that the taxonomy term“Furniture” will now have two different physical pages specified for it.Namely, a template page for a friendly URL (e.g.,“/Pages/Products.aspx”) and a template page for Catalog URL (e.g.,“/Pages/ItemTemplate.aspx”). Table 6 below shows example mappingsbetween menu items, friendly URLs, physical URLs and associated CatalogURLs.

TABLE 6 Menu Item Friendly URL Physical URL Catalog URL “Home” //Pages/Default.aspx (none)  “About Us” /about /Pages/Misc/About.aspx(none)  “Our Products” /products /Pages/Products.aspx (none)  “Electronics” /products/electronics /Pages/ProductsTemplate.aspx/Pages/ItemTemplate.aspx    “TVs” /products/electronics//Pages/ElectronicsTemplate.aspx /Pages/ItemTemplate.aspx tvs    “Phones”/products/electronics/ /Pages/ElectronicsTemplate.aspx/Pages/ItemTemplate.aspx phones   “Furniture” /products/furniture/Pages/ProductsTemplate.aspx /Pages/ItemTemplate.aspx   “Outdoors”/products/outdoors /Pages/ProductsTemplate.aspx /Pages/ItemTemplate.aspx “Contact” (none) /Forms/Contact.aspx (none)

FIG. 6 illustrates an exemplary web page 600 for a given item in aproduct catalog. As shown in FIG. 6, a page corresponding to aparticular item may include item properties such as, a SKU number, arating, an item title (e.g., “Red Sofa”) and the like. In certainembodiments, the item properties may be used to generate the suffix forthe catalog URL.

As discussed above, the templates for the friendly URL and the catalogURL show different content depending on the URL. For the friendly URL,the template is driven by the term in the hierarchy (e.g. “Furniture”),which is identified using ID's that get appended when the URL isrewritten. Thus, for example, the physical URL associated with thefriendly URL may be written as:“http://example.com/Pages/ProductsTemplate.aspx?TermStoreId=1001&TermSetId=3013&TermId=4017.”

For the catalog URL, the template is driven by the term as well as thesuffix (e.g., sku1096/red-sofa). An exemplary URL may be written as:“http://example.com/Pages/ItemTemplate.aspx?TermStoreId=1001&TermSetId=3013&TermId=4017&UrlSuffix=/sku01096/red-sofa.”In certain embodiments, the suffix may be a SKU number of a particularproduct, a given name of the particular product, or an arbitrary numberassigned by the user (i.e., listed in product database). In sum, a useris given the choice as to how the ending portion of the friendly URL isto appear. For example, a user may wish to use a friendly name of aparticular item (e.g., “Sofa”) so that the item and its associatedfriendly URL may be discovered when the term “Sofa” is input in a searchengine. In certain embodiments, the text that appears at the end of thefriendly URL is a property of the term to which the product relates to.For example, “Sofa” may be a property of the term “Furniture” in theterm store.

In embodiments, the controls on a template page such as page 600, caninterpret a UrlSuffix parameter in different ways. For example, for animage gallery scenario, some customized controls might see a URL like“UrlSuffix=/BrownBear”, and then follow a mapping to display an imageresource at “example.com/Images/BrownBear.jpg”. For a blog scenario, thecustomized controls might see “UrlSuffix=/2012/01/02/MyThoughtsToday”and extract the date Jan. 2, 2012, and then display the blog postingfrom that day.

Behind the scenes, the mapping is interpreted both as a forward rule(i.e., a catalog URL points to an item to display) and as a reverse rule(i.e., an item points to a catalog URL). For example, when the searchengine crawls the catalog, it may only see the raw item information(e.g. “Red Sofa” and “sku01096”). In order to display the search resultson the page, a rule is applied to reassemble the fields into a completecatalog URL.

FIG. 7A illustrates an exemplary user interface 700 for displaying andediting the properties of a taxonomy term including catalog URLsaccording to one or more embodiments. As shown in FIG. 7A, the userinterface 700 may display the properties of a friendly URL versus acatalog URL mapping. In embodiments, the user does not need to assignthe “Catalog Page for This Term” setting for every single term. Byassigning the “Default Catalog Page for Child Terms” the user canspecify a single URL that affects an entire sub-tree although this canbe overridden where necessary. Additionally, as shown in FIG. 7A, the“Navigation Menu Item Title” text input box contains text that isdifferent from the actual “Taxonomy Term Name” as the “Customize” optionhas been selected. Accordingly, the phrase “Our Products” will show upin a menu item on the webpage instead of the actual term name“Products.”

FIG. 7B illustrates an exemplary user interface 750 for editing catalogitem properties in a product database. For example, user interface 750shows that the item “Red Sofa” appears in the product catalog database.However, because “Red Sofa” is a particular item, it does not have anassociated term in the term set. As such, the item “Red Sofa” is taggedwith the term “Furniture” as shown in “Item Category” field of FIG. 7B(i.e., the “Item Category” field has a new assigned value of“Furniture”). Tagging the item in such a way causes the item “Red Sofa”to be part of the “Furniture” category in the taxonomy. There is notaxonomy term called “Red Sofa”. As also shown, the user interfaceenables a user to set a unique title, item number, image, and the likefor each specific item.

In embodiments, one or more fields in the user interface 750 are used toappend the one or more suffixes to the friendly URL. For example, the“Item Number” field will create the “sku01096” part of a URL, and the“Title” field will create a “red-sofa” part of the URL. If the “Title”field was added first, then the URL would be“/products/furniture/red-sofa/sku01096”. However, if the “Item Number”field was not added at all to the user interface 750, the URL would be“/products/furniture/red-sofa/”.

The embodiments and functionalities described herein may operate via amultitude of computing systems including, without limitation, wired andwireless computing systems, mobile computing systems (e.g., mobiletelephones, netbooks, tablet or slate type computers, and laptopcomputers). FIG. 8 illustrates an exemplary tablet computing device 800that may execute one or more embodiments disclosed herein. In addition,the embodiments and functionalities described herein may operate overdistributed systems (e.g., cloud-based computing systems), whereapplication functionality, memory, data storage and retrieval andvarious processing functions may be operated remotely from each otherover a distributed computing network, such as the Internet or anintranet. User interfaces and information of various types may bedisplayed via on-board computing device displays or via remote displayunits associated with one or more computing devices. For example userinterfaces and information of various types may be displayed andinteracted with on a wall surface onto which user interfaces andinformation of various types are projected. Interaction with themultitude of computing systems with which embodiments of the inventionmay be practiced include, keystroke entry, touch screen entry, voice orother audio entry, gesture entry where an associated computing device isequipped with detection (e.g., camera) functionality for capturing andinterpreting user gestures for controlling the functionality of thecomputing device, and the like. FIGS. 9 through 11 and the associateddescriptions provide a discussion of a variety of operating environmentsin which embodiments of the present disclosure may be practiced.However, the devices and systems illustrated and discussed with respectto FIGS. 9 through 11 are for purposes of example and illustration andare not limiting of a vast number of computing device configurationsthat may be utilized for practicing embodiments of the presentdisclosure, described herein.

FIG. 9 is a block diagram illustrating exemplary physical components ofa computing device 900 with which embodiments of the present disclosuremay be practiced. The computing device components described below may besuitable for the computing devices described above. In a basicconfiguration, the computing device 900 may include at least oneprocessing unit 902 and a system memory 904. Depending on theconfiguration and type of computing device, the system memory 904 maycomprise, but is not limited to, volatile storage (e.g., random accessmemory), non-volatile storage (e.g., read-only memory), flash memory, orany combination. The system memory 904 may include an operating system905, one or more program modules 906, which are suitable for runningapplications 920. The operating system 905, for example, may be suitablefor controlling the operation of the computing device 900. Furthermore,embodiments of the present disclosure may be practiced in conjunctionwith a graphics library, other operating systems, or any otherapplication program and is not limited to any particular application orsystem. This basic configuration is illustrated in FIG. 9 by thosecomponents within a dashed line 908. The computing device 900 may haveadditional features or functionality. For example, the computing device900 may also include additional data storage devices (removable and/ornon-removable) such as, for example, magnetic disks, optical disks, ortape. Such additional storage is illustrated in FIG. 9 by a removablestorage device 909 and a non-removable storage device 910.

As stated above, a number of program modules and data files may bestored in the system memory 904. While executing on the processing unit902, the program modules 906 may perform processes including, forexample, one or more of the stages of the methods described herein. Theaforementioned process is an example, and the processing unit 902 mayperform other processes. Other program modules that may be used inaccordance with embodiments of the present disclosure may includeelectronic mail and contacts applications, word processing applications,spreadsheet applications, database applications, slide presentationapplications, drawing or computer-aided application programs, etc.

Generally, consistent with embodiments of the present disclosure,program modules may include routines, programs, components, datastructures, and other types of structures that may perform particulartasks or that may implement particular abstract data types. Moreover,embodiments of the present disclosure may be practiced with othercomputer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and the like.Embodiments of the present disclosure may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules may be located inboth local and remote memory storage devices.

Furthermore, embodiments of the present disclosure may be practiced inan electrical circuit comprising discrete electronic elements, packagedor integrated electronic chips containing logic gates, a circuitutilizing a microprocessor, or on a single chip containing electronicelements or microprocessors. For example, embodiments of the presentdisclosure may be practiced via a system-on-a-chip (SOC) where each ormany of the components illustrated in FIG. 9 may be integrated onto asingle integrated circuit. Such an SOC device may include one or moreprocessing units, graphics units, communications units, systemvirtualization units and various application functionality all of whichare integrated (or “burned”) onto the chip substrate as a singleintegrated circuit. When operating via an SOC, the functionality,described herein may be operated via application-specific logicintegrated with other components of the computing device 900 on thesingle integrated circuit (chip). Embodiments of the present disclosuremay also be practiced using other technologies capable of performinglogical operations such as, for example, AND, OR, and NOT, including butnot limited to mechanical, optical, fluidic, and quantum technologies.In addition, embodiments of the present disclosure may be practicedwithin a general purpose computer or in any other circuits or systems.

Embodiments of the present disclosure, for example, may be implementedas a computer process (method), a computing system, or as an article ofmanufacture, such as a computer program product or computer readablemedia. The computer program product may be a computer storage mediareadable by a computer system and encoding a computer program ofinstructions for executing a computer process.

The term computer readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Thesystem memory 904, the removable storage device 909, and thenon-removable storage device 910 are all computer storage media examples(i.e., memory storage.) Computer storage media may include, but is notlimited to, RAM, ROM, electrically erasable read-only memory (EEPROM),flash memory or other memory technology, CD-ROM, digital versatile disks(DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store information and which can be accessedby the computing device 900. Any such computer storage media may be partof the computing device 900. The computing device 900 may also have oneor more input device(s) 912 such as a keyboard, a mouse, a pen, a soundinput device, a touch input device, etc. The output device(s) 914 suchas a display, speakers, a printer, etc. may also be included. Theaforementioned devices are examples and others may be used.

The term computer readable media as used herein may also includecommunication media. Communication media may be embodied by computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and includes any information delivery media. The term“modulated data signal” may describe a signal that has one or morecharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia may include wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared, and other wireless media. The computing device 900 may includeone or more communication connections 916 allowing communications withother computing devices 918. Examples of suitable communicationconnections 916 include, but are not limited to, RF transmitter,receiver, and/or transceiver circuitry; universal serial bus (USB),parallel, or serial ports, and other connections appropriate for usewith the applicable computer readable media.

FIGS. 10A and 10B illustrate a mobile computing device 1000, forexample, a mobile telephone, a smart phone, a tablet personal computer,a laptop computer, and the like, with which embodiments of the presentdisclosure may be practiced. With reference to FIG. 10A, an exemplarymobile computing device 1000 for implementing the embodiments isillustrated. In a basic configuration, the mobile computing device 1000is a handheld computer having both input elements and output elements.The mobile computing device 1000 typically includes a display 1005 andone or more input buttons 1010 that allow the user to enter informationinto the mobile computing device 1000. The display 1005 of the mobilecomputing device 1000 may also function as an input device (e.g., atouch screen display). If included, an optional side input element 1015allows further user input. The side input element 1015 may be a rotaryswitch, a button, or any other type of manual input element. Inalternative embodiments, mobile computing device 1000 may incorporatemore or less input elements. For example, the display 1005 may not be atouch screen in some embodiments. In yet another alternative embodiment,the mobile computing device 1000 is a portable phone system, such as acellular phone. The mobile computing device 1000 may also include anoptional keypad 1035. Optional keypad 1035 may be a physical keypad or a“soft” keypad generated on the touch screen display. In variousembodiments, the output elements include the display 1005 for showing agraphical user interface (GUI), a visual indicator 1020 (e.g., a lightemitting diode), and/or an audio transducer 1025 (e.g., a speaker). Insome embodiments, the mobile computing device 1000 incorporates avibration transducer for providing the user with tactile feedback. Inyet another embodiment, the mobile computing device 1000 incorporatesinput and/or output ports, such as an audio input (e.g., a microphonejack), an audio output (e.g., a headphone jack), and a video output(e.g., a HDMI port) for sending signals to or receiving signals from anexternal device.

Although described herein in combination with the mobile computingdevice 1000, in alternative embodiments, features of the presentdisclosure may be used in combination with any number of computersystems, such as desktop environments, laptop or notebook computersystems, multiprocessor systems, micro-processor based or programmableconsumer electronics, network PCs, mini computers, main frame computersand the like. Embodiments of the present disclosure may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network in a distributed computing environment; programsmay be located in both local and remote memory storage devices. Tosummarize, any computer system having a plurality of environmentsensors, a plurality of output elements to provide notifications to auser and a plurality of notification event types may incorporateembodiments of the present disclosure.

FIG. 10B is a block diagram illustrating the architecture of oneembodiment of a mobile computing device. That is, the mobile computingdevice 1000 can incorporate a system (i.e., an architecture) 1002 toimplement some embodiments. In one embodiment, the system 1002 isimplemented as a “smart phone” capable of running one or moreapplications (e.g., browser, e-mail, calendaring, contact managers,messaging clients, games, and media clients/players). In someembodiments, the system 1002 is integrated as a computing device, suchas an integrated personal digital assistant (PDA) and wireless phone.

One or more application programs 1066 may be loaded into the memory 1062and run on or in association with the operating system 1064. Examples ofthe application programs include phone dialer programs, e-mail programs,personal information management (PIM) programs, word processingprograms, spreadsheet programs, Internet browser programs, messagingprograms, and so forth. The system 1002 also includes a non-volatilestorage area 1068 within the memory 1062. The non-volatile storage area1068 may be used to store persistent information that should not be lostif the system 1002 is powered down. The application programs 1066 mayuse and store information in the non-volatile storage area 1068, such ase-mail or other messages used by an e-mail application, and the like. Asynchronization application (not shown) also resides on the system 1002and is programmed to interact with a corresponding synchronizationapplication resident on a host computer to keep the information storedin the non-volatile storage area 1068 synchronized with correspondinginformation stored at the host computer. As should be appreciated, otherapplications may be loaded into the memory 1062 and run on the mobilecomputing device 1000.

The system 1002 has a power supply 1070, which may be implemented as oneor more batteries. The power supply 1070 might further include anexternal power source, such as an AC adapter or a powered docking cradlethat supplements or recharges the batteries.

The system 1002 may also include a radio 1072 that performs the functionof transmitting and receiving radio frequency communications. The radio1072 facilitates wireless connectivity between the system 1002 and the“outside world”, via a communications carrier or service provider.Transmissions to and from the radio 1072 are conducted under control ofthe operating system 1064. In other words, communications received bythe radio 1072 may be disseminated to the application programs 1066 viathe operating system 1064, and vice versa.

The radio 1072 allows the system 1002 to communicate with othercomputing devices, such as over a network. The radio 1072 is one exampleof communication media. Communication media may typically be embodied bycomputer readable instructions, data structures, program modules, orother data in a modulated data signal, such as a carrier wave or othertransport mechanism, and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. The term computer readable media as used herein includesboth storage media and communication media.

This embodiment of the system 1002 provides notifications using thevisual indicator 1020 that can be used to provide visual notificationsand/or an audio interface 1074 producing audible notifications via theaudio transducer 1025. In the illustrated embodiment, the visualindicator 1020 is a light emitting diode (LED) and the audio transducer1025 is a speaker. These devices may be directly coupled to the powersupply 1070 so that when activated, they remain on for a durationdictated by the notification mechanism even though the processor 1060and other components might shut down for conserving battery power. TheLED may be programmed to remain on indefinitely until the user takesaction to indicate the powered-on status of the device. The audiointerface 1074 is used to provide audible signals to and receive audiblesignals from the user. For example, in addition to being coupled to theaudio transducer 1025, the audio interface 1074 may also be coupled to amicrophone to receive audible input, such as to facilitate a telephoneconversation. In accordance with embodiments of the present disclosure,the microphone may also serve as an audio sensor to facilitate controlof notifications, as will be described below. The system 1002 mayfurther include a video interface 1076 that enables an operation of anon-board camera 1030 to record still images, video stream, and the like.

A mobile computing device 1000 implementing the system 1002 may haveadditional features or functionality. For example, the mobile computingdevice 1000 may also include additional data storage devices (removableand/or non-removable) such as, magnetic disks, optical disks, or tape.Such additional storage is illustrated in FIG. 10B by the non-volatilestorage area 1068. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data.

Data/information generated or captured by the mobile computing device1000 and stored via the system 1002 may be stored locally on the mobilecomputing device 1000, as described above, or the data may be stored onany number of storage media that may be accessed by the device via theradio 1072 or via a wired connection between the mobile computing device1000 and a separate computing device associated with the mobilecomputing device 1000, for example, a server computer in a distributedcomputing network, such as the Internet. As should be appreciated suchdata/information may be accessed via the mobile computing device 1000via the radio 1072 or via a distributed computing network. Similarly,such data/information may be readily transferred between computingdevices for storage and use according to well-known data/informationtransfer and storage means, including electronic mail and collaborativedata/information sharing systems.

FIG. 11 illustrates one embodiment of the architecture of a system forproviding converted documents to one or more client devices, asdescribed above. In certain embodiments, the converted documents may bestored in different communication channels or other storage types. Forexample, various documents, including the converted documents, may bestored using a directory service 1122, a web portal 1124, a mailboxservice 1126, an instant messaging store 1128, or a social networkingsite 1130. The various components of the system 100 use any of thesetypes of systems or the like for enabling data utilization, as describedherein. A server 1120 may provide the converted paragraphs to clients.The server 1120 may provide the converted paragraphs and the statusupdates over the web to clients through a network 1115. By way ofexample, the client computing device 1118 may be implemented as thecomputing device 1100 and embodied in a personal computer 1118 a, atablet computing device 1118 b and/or a mobile computing device 1118 c(e.g., a smart phone). Any of these embodiments of the client computingdevice 1118 may obtain content from the store 1116. In variousembodiments, the types of networks used for communication between thecomputing devices that make up the present disclosure include, but arenot limited to, an internet, an intranet, wide area networks (WAN),local area networks (LAN), and virtual private networks (VPN). In thepresent application, the networks include the enterprise network and thenetwork through which the client computing device accesses theenterprise network (i.e., the client network). In one embodiment, theclient network is part of the enterprise network. In another embodiment,the client network is a separate network accessing the enterprisenetwork through externally available entry points, such as a gateway, aremote access protocol, or a public or private internet address.

One skilled in the relevant art may recognize, however, that theembodiments may be practiced without one or more of the specificdetails, or with other methods, resources, materials, etc. In otherinstances, well known structures, resources, or operations have not beenshown or described in detail merely to avoid obscuring aspects of theembodiments.

The description and illustration of one or more embodiments provided inthis application are not intended to limit or restrict the scope of theinvention as claimed in any way. The embodiments, examples, and detailsprovided in this application are considered sufficient to conveypossession and enable others to make and use the best mode of claimedinvention. The claimed invention should not be construed as beinglimited to any embodiment, example, or detail provided in thisapplication. Regardless of whether shown and described in combination orseparately, the various features (both structural and methodological)are intended to be selectively included or omitted to produce anembodiment with a particular set of features. Having been provided withthe description and illustration of the present application, one skilledin the art may envision variations, modifications, and alternateembodiments falling within the spirit of the broader aspects of thegeneral inventive concept embodied in this application that do notdepart from the broader scope of the claimed invention.

We claim:
 1. A method comprising: assigning a navigation property to aterm in a navigation term set that comprises a plurality of termsarranged in a hierarchical taxonomy; associating the navigation propertywith a navigation tree node and a physical uniform resource locator tocreate a mapping, wherein the physical uniform resource locatorcomprises a base uniform resource locator for a website; generating afirst friendly uniform resource locator that is an alias for thephysical uniform resource locator by appending the term from thehierarchical taxonomy to the base uniform resource locator of thephysical uniform resource locator based on the mapping associating thenavigation property and the physical uniform resource locator; providingthe first friendly uniform resource locator for access to the website;receiving an update to the navigation property; when the update isreceived, generating a second friendly uniform resource locator based onthe mapping by modifying at least an appended term to the base uniformresource locator of the first friendly uniform resource locator, whereinthe appended term is modified according to the update to the navigationproperty; and providing the second friendly uniform resource locator foraccess to the website based on the update to the navigation property. 2.The method according to claim 1, further comprising mapping the secondfriendly uniform resource locator to a physical uniform resourcelocator.
 3. The method according to claim 1, wherein the update to thenavigation property comprises modifying the term.
 4. The methodaccording to claim 1, wherein the update to the navigation propertycomprises modifying an association of the term within the hierarchicaltaxonomy.
 5. The method according to claim 4, wherein the modifying ofthe association further comprises changing a parent node of a nodeassociated with the term.
 6. The method according to claim 1, whereinthe generating of the first friendly uniform resource locator generatesthe first friendly uniform resource locator by appending the term and atleast one other term from the hierarchical taxonomy in accordance withthe navigation property.
 7. The method according to claim 1, wherein thenavigation term set further comprises a second navigation propertyassociated with a second term arranged in the hierarchical taxonomy,wherein the second navigation property is associated with the physicaluniform resource locator, and wherein the method further comprises:generating a third friendly uniform resource locator that is an aliasfor the physical uniform resource locator by appending at least thesecond term to the base uniform resource locator of the physical uniformresource locator.
 8. A system comprising: at least one processor; and amemory operatively connected with the at least one processor, whereinthe memory stores computer-executable instructions that, when executedby the at least one processor, causes the at least one processor toexecute a method that comprises: assigning a navigation property to aterm in a navigation term set that comprises a plurality of termsarranged in a hierarchical taxonomy; associating the navigation propertywith a navigation tree node and a physical uniform resource locator tocreate a mapping, wherein the physical uniform resource locatorcomprises a base uniform resource locator for a website; generating afirst friendly uniform resource locator that is an alias for thephysical uniform resource locator by appending the term from thehierarchical taxonomy to the base uniform resource locator of thephysical uniform resource locator based on the mapping associating thenavigation property and the physical uniform resource locator; providingthe first friendly uniform resource locator for access to the website;receiving an update to the navigation property; when the update isreceived, generating a second friendly uniform resource locator based onthe mapping by modifying at least an appended term to the base uniformresource locator of the first friendly uniform resource locator, whereinthe appended term is modified according to the update to the navigationproperty; and providing the second friendly uniform resource locator foraccess to the website based on the update to the navigation property. 9.The system according to claim 8, wherein the method further comprisesmapping the second friendly uniform resource locator to a physicaluniform resource locator.
 10. The system according to claim 8, whereinthe update to the navigation property comprises modifying the term. 11.The system according to claim 8, wherein the update to the navigationproperty comprises modifying an association of the term within thehierarchical taxonomy.
 12. The system according to claim 11, wherein themodifying of the association further comprises changing a parent node ofa node associated with the term.
 13. The system according to claim 8,wherein the generating of the first friendly uniform resource locatorgenerates the first friendly uniform resource locator by appending theterm and at least one other term from the hierarchical taxonomy inaccordance with the navigation property.
 14. The system according toclaim 8, wherein the navigation term set further comprises a secondnavigation property associated with a second term arranged in thehierarchical taxonomy, wherein the second navigation property isassociated with the physical uniform resource locator, and wherein themethod further comprises: generating a third friendly uniform resourcelocator that is an alias for the physical uniform resource locator byappending at least the second term to the base uniform resource locatorof the physical uniform resource locator.
 15. A method comprising:assigning a navigation property to a term in a navigation term set thatcomprises a plurality of terms arranged in a hierarchical taxonomy;associating the navigation property with a navigation tree node and aphysical uniform resource locator to create a mapping, wherein thephysical uniform resource locator comprises a base uniform resourcelocator for a website; generating a first friendly uniform resourcelocator that is an alias for the physical uniform resource locator byappending the term and at least one other term from the hierarchicaltaxonomy to the base uniform resource locator of the physical uniformresource locator based on the mapping associating the navigationproperty and the physical uniform resource locator; providing the firstfriendly uniform resource locator for access to the website; receivingan update to the navigation property; when the update is received,generating a second friendly uniform resource locator based on themapping by modifying at least an appended term to the base uniformresource locator of the first friendly uniform resource locator, whereinthe appended term is modified according to the update to the navigationproperty; and providing the second friendly uniform resource locator foraccess to the website based on the update to the navigation property.16. The method according to claim 15, further comprising generating thehierarchical taxonomy for the navigation term set.
 17. The methodaccording to claim 15, wherein the update to the navigation propertycomprises modifying the term.
 18. The method according to claim 15,wherein the update to the navigation property comprises modifying anassociation of the term and the at least one other term within thehierarchical taxonomy.
 19. The method according to claim 15, wherein themodifying of the association further comprises changing a parent node ofa node associated with one or more of the term and the at least oneother term.
 20. The method according to claim 15, wherein the assigningof the navigation property further comprises assigning a navigationproperty to the at least one other term.